System and method for securing sensitive information during completion of a transaction

ABSTRACT

A system and method for securing a Radio Frequency (RF) transaction using a proxy code, which is permanently assigned to the RF identification device (RFID) transaction account number. An account issuer permanently assigns the proxy code to a transaction account correlated to the RFID transaction device. The proxy code is uploaded onto the transaction device for later use in completing a transaction request. During transaction completion, the proxy code is provided to a merchant system in lieu of any sensitive transaction account information. Since the proxy code is permanently assigned, the number need not be changed or updated once uploaded into a payment device or merchant system. Since the proxy code contains no sensitive information, the sensitive information related to the transaction account is secured from theft where the merchant system internal security measures may fail.

CROSS REFERENCE TO RELATED APPLICATIONS

This invention is a continuation in part of, and claims priority to U.S. patent application Ser. No. 10/192,488, entitled “SYSTEM AND METHOD FOR PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed on Jul. 9, 2002 (which itself claims priority to U.S. Provisional Patent Application No. 60/304,216, filed Jul. 10, 2001), and to U.S. patent application Ser. No. 10/340,352, entitled “SYSTEM AND METHOD FOR INCENTING PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed Jan. 10, 2003 (which itself claims priority to U.S. Provisional Patent Application No. 60/396,577, filed Jul. 16, 2002), all of which are incorporated herein by reference.

FIELD OF INVENTION

This invention generally relates to securing a transaction involving radio frequency identification (RFID) technology. More particularly, the invention pertains to a system and method for securing the RFID enabled transaction using a code or number which hides the underlying payment device information from the merchant system.

BACKGROUND OF INVENTION

Like barcode and voice data entry, RFID is a contactless information acquisition technology. RFID systems are wireless, and are usually extremely effective in hostile environments where conventional acquisition methods often fail. RFID has established itself in a wide range of markets, such as, for example, the high-speed reading of railway containers, tracking moving objects such as livestock or automobiles, and retail inventory applications. As such, RFID technology has become a primary focus in automated data collection, identification and analysis systems worldwide.

Of late, companies are increasingly embodying RFID data acquisition technology in a fob or tag for use in completing financial transactions. A typical RFID fob is ordinarily a self-contained device, which may take the shape of any portable form factor. The RFID fob may include a transponder for transmitting information during a transaction. In some instances, a battery may be included in the fob to power the transponder, in which case the internal circuitry of the fob (including the transponder) may draw its operating power from the battery power source. Alternatively, the fob may gain its operating power directly from an RF interrogation signal. U.S. Pat. No. 5,053,774, issued to Schuermann, describes a typical transponder RF interrogation system which may be found in the prior art. The Schuermann patent generally describes the powering technology surrounding conventional transponder structures. U.S. Pat. No. 4,739,328 discusses a method by which a conventional transponder may respond to a RF interrogation signal. Other typical modulation techniques which may be used include, for example, ISO/IEC 14443 and the like.

In the conventional fob powering technologies used, the fob is typically activated upon presenting the fob into an interrogation signal. In this regard, the fob may be activated irrespective of whether the user desires such activation. Alternatively, the fob may have an internal power source such that interrogation by the reader for activation of the fob is not required.

One of the more visible uses of the RFID technology is the introduction of Exxon/Mobil's Speedpass® and Shell's EasyPay® products. These products use transponders, placed in a fob or tag, which enable automatic identification of the user when the fob is presented at a merchant's Point of Sale (POS) device, for example, when attempting to complete a transaction. During the transaction completion, information from the RFID fob is ordinarily passed to the POS, which delivers the information to a merchant system.

To complete the transaction, fob identification data typically may be passed to a third-party server database. The third-party server may reference the identification data to a customer (e.g., user) credit or debit account. In an exemplary processing method, the third-party server may seek authorization for the transaction by passing the transaction and account data to an authorizing entity, such as for example an “acquirer” or account issuer. Once the server receives authorization from the authorizing entity, the authorizing entity sends clearance to the POS device for completion of the transaction.

In addition to sending the information to an issuer system for verification, the merchant system may store the information in a merchant system database for later reference. For example, where the transaction device user is a repeat customer, the transaction device user may wish to complete the transaction using transaction account information previously submitted to the merchant system. Since the account information is stored on the merchant system, the user need not provide the information to a merchant to complete subsequent transactions. Instead, the user may indicate to the merchant to use the transaction account information stored on the merchant system for transaction completion.

In another typical example, the merchant system may store the transaction account information for later reference when the transaction device user establishes a “recurring billing” account. In this instance, the merchant may periodically charge a user for services rendered or goods purchased. The user may authorize the merchant system to seek satisfaction of the bill using the transaction account information. The merchant may thereby send a transaction request regarding the bill to an account provider, or a third-party server.

To lessen the financial impact of fraudulent transactions in the RFID environment, fob issuers have focused much effort on securing RFID transactions. Many of the efforts have focused on securing the transaction account or related data during transmission from the user to the merchant, or from the merchant to third-party server or account provider system. For example, one conventional method for securing RFID transactions involves requiring the device user to provide a secondary form of identification during transaction completion. The RFID transaction device user may be asked to enter a personal identification number (PIN) into a keypad. The PIN may then be verified against a number associated with the user or the RFID transaction device, wherein the associated number is stored in an account issuer database. If the PIN number provided by the device user matches the associated number, then the transaction may be cleared for completion.

One problem with the issuer's efforts in securing RFID transactions is that they typically do not focus on the ways to guard the transaction account information stored on the merchant system from theft. As noted, the merchant may typically store on a merchant database the information received from the transaction device during a transaction. Such information may be sensitive information concerning the fob user or the fob user's account. Should the fob user's sensitive information be retrieved from the merchant system without authorization, the fob user or issuer may be subjected to fraudulent activity. The ability to secure the sensitive information stored on the merchant system is limited by the security measures taken by the merchant in securing its merchant system database. Consequently, the account provider often has little influence over the security of the account information once the information is provided to the merchant system.

As such, a need exists for a method of securing sensitive transaction account information which permits the account provider to have a significant influence on the security of the fob user information stored on a merchant system. A suitable system may secure the sensitive information irrespective of the merchant system.

SUMMARY OF INVENTION

A system and method for securing transactions is described which addresses the problems found in conventional transaction securing methods. The securing method described herein includes providing a proxy code to a merchant system during a transaction instead of providing sensitive transaction account information. A transaction device in accordance with the invention provides the proxy code to the merchant system contemporaneously with a transaction request. The merchant system may receive the proxy code and correlate the proxy code to a user or transaction in the merchant system. The merchant system may store the proxy code in a merchant database for later reference.

The proxy code does not include any sensitive information about the transaction device user or user transaction account. Instead the merchant system receives a proxy code, which takes the place of that sensitive information ordinarily received during transaction completion. In other words, certain information such as the user's actual account number is never transmitted to the merchant. Thus, the user's account number is not available should the merchant system be compromised.

In accordance with one exemplary embodiment of the invention, a radio frequency identification (RFID) transaction device is used to complete a transaction. The RFID transaction device may be interrogated by a RFID reader operable to provide a RF interrogation signal for powering a transponder system. The RFID reader may receive the proxy code instead of sensitive transaction device information, and the merchant may receive the transaction device proxy code from the RFID transaction device and provide the proxy code to an authorizing agent, such as an acquirer or an account issuer, for verification. For example, the authorizing agent may verify that the proxy code corresponds to a valid transaction account on the account provider system. The authorizing agent may use the proxy code to locate the appropriate verifying (e.g., “validating”) information for confirming the transaction account validity. Once the authorizing agent verifies the validity of the transaction account using the proxy code, the authorizing entity (e.g., account issuer or acquirer) may provide authorization to the merchant that a transaction may be completed.

In one exemplary embodiment, the RFID reader may additionally be validated. In this instance, the RFID reader may be provided a RFID reader authentication tag which may be used to validate the reader. During a transaction completion, the RFID reader receives the RFID transaction device proxy code, the reader may provide the transaction device proxy code, and the reader authentication tag to an authorizing agent, such as an acquirer. In similar manner as with the transaction account, the acquirer may then validate that the RFID reader is an authorized reader for facilitating a RF transaction with the account issuer. If the RFID reader is validated, the acquirer may then provide the RFID transaction device identifier to an account provider for RFID device verification. The account issuer may then verify that the RFID transaction device is authorized to complete the requested transaction. Alternatively, the reader may be directly validated by the account issuer.

These features and other advantages of the system and method, as well as the structure and operation of various exemplary embodiments of the system and method, are described below.

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings, wherein like numerals depict like elements, illustrate exemplary embodiments of the present invention, and together with the description, serve to explain the principles of the invention. In the drawings:

FIG. 1 illustrates an exemplary RFID transaction system depicting exemplary components for use in a secure RFID transaction completed in accordance with the present invention; and

FIG. 2 depicts an exemplary flowchart of an overview of a exemplary method for securing a RFID transaction in accordance with the present invention.

DETAILED DESCRIPTION

The present invention may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. Such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the present invention may employ various integrated circuit components (e.g., memory elements, processing elements, logic elements, look-up tables, and the like), which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the present invention may be implemented with any programming or scripting language such as C, C++, Java, COBOL, assembler, PERL, extensible markup language (XML), JavaCard and MULTOS with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the present invention may employ any number of conventional techniques for data transmission, signaling, data processing, network control, encryption and the like. For a basic introduction on cryptography, review a text written by Bruce Schneier entitled “Applied Cryptography: Protocols, Algorithms, and Source Code in C,” published byjohn Wiley & Sons (second edition, 1996), herein incorporated by reference.

The exemplary network disclosed herein may include any system for exchanging data or transacting business, such as the Internet, an intranet, an extranet, WAN, LAN, satellite communications, and/or the like. It is noted that the network may be implemented as other types of networks, such as an interactive television network (ITN). Further still, the terms “Internet” or “network” may refer to the Internet, any replacement, competitor or successor to the Internet, or any public or private inter-network, intranet or extranet that is based upon open or proprietary protocols. Specific information related to the protocols, standards, and application software utilized in connection with the Internet may not be discussed herein. For further information regarding such details, see, for example, Dilip Naik, “Internet Standards and Protocols” (1998); “Java 2 Complete”, various authors, (Sybex 1999); Deborah Ray and Eric Ray, “Mastering HTML 4.0” (1997); Loshin, “TCP/IP Clearly Explained” (1997). All of these texts are hereby incorporated by reference.

By communicating, a signal may travel to/from one component to another. The components may be directly connected to each other or may be connected through one or more other devices or components. The various coupling components for the devices can include but are not limited to the Internet, a wireless network, a conventional wire cable, an optical cable or connection through air, water, or any other medium that conducts signals, and any other coupling device or medium.

Where required, the system user may interact with the system via any input device such as, a keypad, keyboard, mouse, biometric device, kiosk, personal digital assistant, handheld computer (e.g., Palm Pilot®, Blueberry®), cellular phone and/or the like. Similarly, the invention could be used in conjunction with any type of personal computer, network computer, work station, minicomputer, mainframe, or the like, running any operating system such as any version of Windows, Windows NT, Windows 2000, Windows 98, Windows 95, MacOS, OS/2, BeOS, Linux, UNIX, Solaris, or the like. Moreover, it should be understood that the invention could be implemented using TCP/IP communications protocol, SNA, IPX, Appletalk, IPte, NetBIOS, OSI or any number of communications protocols. Moreover, the transactions discussed herein may include or result in the use, sale, or distribution of any goods, services or information over any network having similar functionality described herein.

A variety of conventional communications media and protocols may be used for data links providing physical connections between the various system components. For example, the data links may be an Internet Service Provider (ISP) configured to facilitate communications over a local loop as is typically used in connection with standard modem communication, cable modem, dish networks, ISDN, Digital Subscriber Lines (DSL), or any wireless communication media. In addition, the merchant system including a merchant point of sale (POS) device and host network may reside on a local area network, which interfaces to a remote network for remote authorization of an intended transaction. The POS may communicate with the remote network via a leased line, such as a T1, D3 line, or the like. Such communications lines are described in a variety of texts, such as, “Understanding Data Communications,” by Gilbert Held, which is incorporated herein by reference.

A transaction device identifier, as used herein, may include any identifier for a transaction device, such as, for example, any hardware, software, code, number, letter, symbol, digital certificate, smart chip, digital signal, analog signal, biometric and/or other identifier/indicia. The device identifier may also be correlated to a user transaction account (e.g., credit, charge debit, checking, savings, reward, loyalty, or the like) maintained by a transaction account provider (e.g., payment authorization center). A typical transaction account identifier (e.g., account number) distinct to a transaction device, may be correlated to a credit or debit account, loyalty account, or rewards account maintained and serviced by such entities as American Express®, Visa®, MasterCard® or the like.

A transaction device identifier or account number may be, for example, a sixteen-digit credit card number, although each credit provider has its own numbering system, such as the fifteen-digit numbering system used by American Express. Each company's credit card numbers comply with that company's standardized format such that the company using a sixteen-digit format will generally use four spaced sets of numbers, as represented by the number “0000 0000 0000 0000.” In a typical example, the first five to seven digits are reserved for processing purposes and identify the issuing bank, card type and, etc. In this example, the last sixteenth digit is used as a sum check for the sixteen-digit number. The intermediary eight-to-ten digits are used to uniquely identify the customer. The account number transaction device may be stored as Track 1 and Track 2 data as defined in ISO/IEC 7813, and further may be created unique to the RFID transaction device. The account number or transaction device may be communicated in Track 1 and Track 2 data, as well.

In one exemplary embodiment, the transaction device may be correlated with a unique RFID transaction device account number. In accordance with the invention, the account number is not provided to a merchant during transaction completion. Instead, the merchant system may be provided a “proxy code” (described below). The transaction device proxy code may be stored on a transaction device database located on the transaction device. The transaction device database may be configured to store multiple proxy codes issued to the RFID transaction device user by the same or different account providing institutions.

To facilitate understanding, the present invention may be described with respect to a credit account. However, it should be noted that the invention is not so limited. Other accounts which facilitate an exchange of goods or services are contemplated to be within the scope of the present invention.

The databases discussed herein may be any type of database, such as relational, hierarchical, object-oriented, and/or the like. Common database products that may be used to implement the databases include DB2 by IBM (White Plains, N.Y.), any of the database products available from Oracle Corporation (Redwood Shores, Calif.), Microsoft Access or MSSQL by Microsoft Corporation (Redmond, Wash.), or any other database product. Databases may be organized in any suitable manner, including as data tables or lookup tables. Association of certain data may be accomplished through any data association technique known and practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in each of the manufacturer and retailer data tables. A “key field” partitions the database according to the high-level class of objects defined by the key field. For example, a certain class may be designated as a key field in both the first data table and the second data table, and the two data tables may then be merged on the basis of the class data in the key field. In this embodiment, the data corresponding to the key field in each of the merged data tables is preferably the same. However, data tables having similar, though not identical, data in the key fields may also be merged by using AGREP, for example.

In accordance with one aspect of the present invention, any suitable data storage technique may be utilized to store data without a standard format. Data sets may be stored using any suitable technique, including, for example, storing individual files using an ISO/IEC 7816-4 file structure; implementing a domain whereby a dedicated file is selected that exposes one or more elementary files containing one or more data sets; using data sets stored in individual files using a hierarchical filing system; data sets stored as records in a single file (including compression, SQL accessible, hashed via one or more keys, numeric, alphabetical by first tuple, etc.); block of binary (BLOB); stored as ungrouped data elements encoded using ISO/IEC 7816-6 data elements; stored as ungrouped data elements encoded using ISO/IEC Abstract Syntax Notation (ASN.1) as in ISO/IEC 8824 and 8825; and/or other proprietary techniques that may include fractal compression methods, image compression methods, etc.

In one exemplary embodiment, the ability to store a wide variety of information in different formats is facilitated by storing the information as a Block of Binary (BLOB). Thus, any binary information can be stored in a storage space associated with a data set. As discussed above, the binary information may be stored on the financial transaction instrument or external to but affiliated with the financial transaction instrument. The BLOB method may store data sets as ungrouped data elements formatted as a block of binary via a fixed memory offset using either fixed storage allocation, circular queue techniques, or best practices with respect to memory management (e.g., paged memory, least recently used, etc.). By using BLOB methods, the ability to store various data sets that have different formats facilitates the storage of data associated with the financial transaction instrument by multiple and unrelated owners of the data sets. For example, a first data set which may be stored may be provided by a first issuer, a second data set which may be stored may be provided by an unrelated second issuer, and yet a third data set which may be stored, may be provided by an third issuer unrelated to the first and second issuer. Each of these three exemplary data sets may contain different information that is stored using different data storage formats and/or techniques. Further, each data set may contain subsets of data which also may be distinct from other subsets.

In addition to the above, the transaction device identifier may be associated with any secondary form of identification configured to allow the consumer to interact or communicate with a payment system. For example, the transaction device identifier may be associated with, for example, an authorization/access code, personal identification number (PIN), Internet code, digital certificate, biometric data, and/or other secondary identification data used to verify a transaction device user identity.

It should be further noted that conventional components of RFID transaction devices may not be discussed herein for brevity. For example, one skilled in the art will appreciate that the RFID transaction device and the RFID reader disclosed herein include traditional transponders, antennas, protocol sequence controllers, modulators/demodulators and the like, necessary for proper RFID data transmission. A suitable RFID transaction device and RFID reader which may be used with this invention are disclosed in U.S. patent application Ser. No. 10/192,488, filed Jul. 9, 2002. As such, those components are contemplated to be included in the scope of the invention.

Various components may be described herein in terms of their “validity.” In this context, a “valid” component is one that is partially or fully authorized for use in completing a transaction request in accordance with the present invention. Contrarily, an “invalid” component is one that is not partially or fully authorized for transaction completion.

Although the present invention is described with respect to validating a transaction device or reader communicating in a RF transaction, the invention is not so limited. The present invention may be used for any device, machine, or article which provides user identifying data to a merchant. Thus, the present invention may be used in any contact or contactless environment where identifying data is transferred to a merchant.

During a typical RFID transaction, a RFID transaction device user may transmit information concerning the user's transaction account to a merchant POS. The information received by the POS may include, for example, the transaction device identifier or account number. The information may further include personal, demographic, biometric or statistical information related to the transaction device user. Upon receiving the information, the merchant POS ordinarily provides the information to a merchant system. The merchant may store the information in a merchant system database for later reference. For example, the merchant system may then reference the transaction device information in the event that a user wishes to complete a transaction by providing the merchant the same identifying information as the merchant has stored on the merchant system.

In most instances, the transaction device information is stored on the merchant system database for an extended period of time. The extended storage is often because the merchant typically may wish to have the information readily available for later reference (e.g., transaction request maintenance, account or transaction request tracking, or the like). The merchant may also desire to archive the transaction device information for later use in preparing promotional offers or solicitations or materials to be provided to the transaction device user.

One key disadvantage of the conventional transaction processing method described above is that the information stored by the merchant is typically “sensitive information.” Sensitive information is that information which the transaction account provider or the transaction device user would want to guard from theft. Sensitive information may be any information or data. The sensitive information may be used to conduct a fraudulent transaction. For example, sensitive information may be the user account number, transaction device identifier, transaction device user personal data or the like. The information may be used for example to complete a transaction by reproducing the sensitive information without authorization. If sensitive information is somehow compromised or stolen, it is easily subjected to fraudulent usage. For example, should an unscrupulous person gain access to the merchant system and steal the transaction device identifier or account number, the person may be able to use the stolen information to place fraudulent charges on the associated transaction account. As such, the merchant may put into place special security measures designed to protect the sensitive information from theft. The merchant ordinarily makes decisions related to securing the sensitive information without consulting the account provider. The transaction account provider often must rely on the effectiveness of the merchant security measures to ensure that the information is not stolen while being stored on the merchant database. If the merchant security methods are ineffective or easily compromised, the sensitive information may be easily stolen.

The present system and method permits the account issuer to control the level of security with which the information stored on the merchant database is protected. An exemplary method in accordance with the present invention is described in FIG. 2. In accordance with the invention, an account provider provides a transaction account to an account user for completing a transaction (step 202). The user may receive the transaction account after the user provides information concerning the user to an account provider system. For example, the user may complete an application for a credit card, and the credit card provider may provide a credit transaction account to the user for transaction completion. The account issuer may then permanently assign a proxy code to the transaction account, so that the proxy code need never be altered or modified during the life of the transaction account (step 204). The account issuer may store the proxy code correlative to the related transaction account. The account issuer may store the proxy code and the account number in a relational database, so that the account issuer could locate the transaction account by referencing the associated permanently assigned proxy code. The account provider may then provide the proxy code to the user, by embodying the proxy code in any presentable form factor such as a credit card, debit card, calling card, loyalty card, key fob, cell phone, key ring, ring, or the like (step 206). The user may then provide the proxy code to a merchant system during the completion of a transaction request (step 208). The manner in which the user provides the transaction account proxy code to the user system may vary in accordance with the form factor in which the proxy is embodied. For example, where the proxy code is embodied in the magnetic stripe of a conventional credit card, the user may provide the proxy code to the merchant by “swiping” the magnetic stripe at a suitable reader as is found in the prior art. Alternatively, the proxy code may be embodied in a transponder system associated with a key fob. In this instance the user may provide the account number to the merchant system by waiving the key fob in proximity to a suitable transponder reader. The reader may provide an interrogation signal to the transponder system to facilitate operation of the transponder system and the transponder reader may provide the proxy code to the merchant system for processing. The merchant may receive the proxy code and store the proxy code in a merchant system database for later reference (step 210). For example, where the user requests that the merchant store the proxy code in reference to a recurring billing account for payment, the merchant may store the proxy code relative to the recurring billing account and periodically use the proxy code to seek payment. The merchant system may then provide the proxy code to the account issuer in a transaction request, under the merchant defined business as usual standard to facilitate completing the transaction (step 212). The account issuer may receive the proxy code and match the proxy code to the corresponding transaction account, which may be stored on a merchant database (step 214). The account provider may then provide to the merchant the information, or funds to complete the transaction (216).

As used herein, the term “proxy code” may include any device, hardware, software, code, number, letter, symbol, digital certificate, smart chip, digital signal, analog signal, biometric and/or other identifier/indicia. The proxy code may also refer to any information provided to, for example, a merchant system during completion of a transaction request, which partially or fully masks the underlying sensitive information from the merchant system. As such, the information provided “masks” the underlying sensitive information related to the transaction account from the merchant system. Particularly, the information provided to the merchant (called “proxy code”, herein) does not include sensitive information like, for example, the transaction account number. Consequently, the merchant system is never provided the sensitive information since the sensitive information is not included in the proxy code. Moreover, the proxy code may take the form of any conventional transaction account identifier. As such, when the merchant receives the proxy code, the merchant system may process the proxy code under business as usual standards. For example, the proxy code may take the form of any conventional transaction device identifier or account number. The merchant system thereby stores the proxy code in the place of the information ordinarily stored under conventional processing methods. Since the proxy code does not include sensitive information, no sensitive information may be stolen should the merchant system be compromised. In this way, the account issuer may substantially eliminate, minimize or control the risks associated with the security of the merchant system being compromised (e.g., fraud transactions, identity theft, etc.).

Another advantage of the present invention is that since the proxy code is permanently associated to a transaction account, the proxy code need never be modified in the merchant system. As such, the present invention eliminates the need to update information on the merchant system every time the related transaction device is lost, stolen, or replaced. More particularly, the replacement device is provided the identical proxy code as was provided to the original transaction device. Consequently, the merchant is provided the identical proxy code in any instance where the user wishes to complete a transaction using the transaction account which the account provider has permanently associated with the proxy code.

For example, the merchant may receive the proxy code and store the proxy code related to a recurring billing account such as a telephone account. Periodically the merchant may bill a transaction device user in accordance with the telephone services provided. The device user may wish to provide the merchant with transaction device information the merchant may use to satisfy the bill. The user may authorize the merchant to store the device information for repeated use in satisfying the bill. In a conventional recurring billing environment, the device information must ordinarily be updated when the user loses the device or the device information expires. That is, the replacement device often is given device information which is often different from the information contained on the original transaction device. However, in accordance with the present invention, the merchant need not update transaction device information because the proxy code is permanently associated with the transaction account.

FIG. 1 illustrates an exemplary RFID transaction system 100 in accordance with the present invention, wherein exemplary components for use in completing a RF transaction are depicted. In general, system 100 may include a RFID transaction device 102 in RF communication with a RFID reader 104 for transmitting data therebetween. The RFID reader 104 may be in further communication with a merchant point of sale (POS 106) device 106 for providing to the POS 106 information received from the RFID transaction device 102. The POS 106 may be in further communication with a merchant system 101, which may include a merchant database 103. Merchant system 101 may be in communication with an acquirer 110 or an account issuer 112 via a network 108 for transmitting transaction request data and receiving authorization concerning transaction completion.

Although the POS 106 is described herein with respect to a merchant point of sale (POS) device, the invention is not to be so limited. Indeed, a merchant POS device is used herein by way of example, and the point of sale device may be any device capable of receiving transaction device account information from the transaction device 102. In this regard, the POS 106 may be any point of interaction device, such as, for example, a merchant terminal, kiosk, user terminal, computer terminal, input/output receiver or reader, etc., enabling the user to complete a transaction using a transaction device 102. The POS device 106 may receive RFID transaction device 102 information and provide the information to a merchant system 101 for processing.

As used herein, an “acquirer” may be any databases and processors (e.g., operated by a third party) for facilitating the routing of a payment request to an appropriate account issuer 112. The acquirer 110 may route the payment request to the account issuer 112 in accordance with a routing number, wherein the routing number corresponds to the account issuer 112. The routing number may be provided by the RFID transaction device 102. The “routing number” in this context may be a unique network address or any similar device for locating an account issuer 112 on a network 108. In one exemplary embodiment, the routing number may typically be stored on one of the “tracks” comprising a magnetic stripe network. For example, the proxy code may be provided in traditional ISO magnetic stripe format. The routing number may be typically stored in Track 1/Track 2 format so that the information may be interpreted by the POS device 106 and merchant system 101. Traditional means of routing the payment request in accordance with the routing number are well understood. As such, the process for using a routing number to provide a payment request will not be discussed herein.

In addition, the account issuer 112 (or account provider) may be any entity which provides a transaction account useful for facilitating completion of a transaction request. The transaction account may be any account which maintains credit, debit, loyalty, direct debit, checking, savings, or the like. The term “issuer” or “account provider” may refer to any entity facilitating payment of a transaction using a transaction device, and which may include systems permitting payment using at least one of a preloaded and non-preloaded transaction device 102. Typical issuers may be American Express, MasterCard, Visa, Discover, and the like.

In general, during operation of system 100, the RFID reader 104 may provide an interrogation signal to transaction device 102 for powering the device 102 and receiving transaction device related information. The interrogation signal may be received at the transaction device antenna 120 and may be further provided to a transponder (not shown). In response, the transaction device processor 114 may retrieve transaction device information from transaction device database 116 for providing to the RFID reader 104 to complete a transaction request. Typically, where the transaction device information includes a transaction device identifier or authentication tag, the identifier and tag may be encrypted prior to providing the information to reader 104.

It should be noted that the RFID reader 104 and the RFID transaction device 102 may engage in mutual authentication prior to transferring any transaction device 102 data to the reader 104. For a detailed explanation of a suitable mutual authentication process for use with the invention, see commonly owned U.S. patent application Ser. No. 10/340,352, entitled “System and Method for Incenting Payment Using Radio Frequency Identification in Contact and Contactless Transactions,” filed Jan. 10, 2003, incorporated by reference in its entirety.

Once the RFID reader 104 receives the transaction device information, the reader 104 provides the information to the merchant POS 106 which provides the information to the merchant system 101. The merchant system 101 may then append the transaction device information with transaction request data and provide the entire transaction request (i.e., transaction request data and transaction device information) to an acquirer 110 or issuer 112 for transaction completion. The transmitting of the information from the transaction device 102 to the acquirer 110 (or issuer 112) may be accomplished in accordance with any conventional method for completing a transaction using contact and wireless data transmission. The acquirer 110 or the issuer 112 may then determine whether to authorize completion of the transaction request in accordance with any business as usual protocol.

In addition to appending the transaction device information to the transaction request data for transaction authorization, conventional merchant systems may also store the transaction device information in a merchant system database (not shown) for later reference. For example, a particular merchant may want to provide special advertisements to the user of the transaction device 102 based on the user's prior purchases at the merchant location. The merchant system 101 may then recall the transaction device information and use the information to prepare, for example, a repeat customer mailing list. In some cases, however, the merchant system 101 often also stores sensitive information related to the user such as, for example, the user's account number (e.g., credit card number) associated with the transaction device 102. This sort of information is typically very easy to use in fraudulent transactions and therefore must be secured from theft. As such, conventional merchant systems use special security methods to safeguard the sensitive information from theft.

The account issuer 112 may provide additional security by assigning a permanent fixed proxy code to the transaction device transaction account (step 204 of FIG. 2). The proxy code may not itself include sensitive information. The proxy code may be associated with a user's transaction account number on a merchant database 103. The account issuer 112 may then provide the proxy code, and not the transaction account number, to the user in a suitable form factor such as, the RFID transaction device 102 discussed above (step 208). The transaction device 102 user may then provide the proxy code to the merchant system 101 during the completion of transaction (step 208). The merchant system 101 may then process the proxy code as a part of a transaction request and may provide the proxy code and to the account issuer 112 for process under merchant and account issuer business as usual standards (step 212). The merchant system 101 may also store the account proxy code for later reference (step 210). Since the proxy code is permanently assigned to the transaction account, the merchant system never need to modify the proxy code on the merchant system 101. The merchant system 101 may store the proxy number on merchant database 103 using any method the merchant ordinarily uses to store customer data.

In assigning the proxy code, the issuer system 112 may first permit a transaction device 102 user to open a transaction account for use in completing a transaction request (step 202). The user may open a transaction account by providing personal or demographic information and the like to an issuer system 112 which may use the information to assign a transaction account and account number to the user. The transaction account may be identified by the account number in the issuer system 112 database (not shown), and the issuer system 112 may be able to reference the transaction account using the account number when authorizing a transaction (step 214).

In this context, the account number is considered sensitive information. The issuer system 112 may then assign a proxy code to the transaction account (step 220). In assigning the proxy code, the issuer system 112 may correlate or match the proxy code to the account number in, for example, a relational database. The algorithm may be such that it will receive the proxy code and operate on the proxy code to convert the proxy code to a number correlated with the transaction account number. Alternatively, the account issuer 112 may store the proxy code in a one to one relationship with the account number. Further still, the account issuer 112 may use any suitable correlation technique that is known which permits the account issuer system to receive one data and associate it with a second data. In other embodiments, the proxy code may be derived from the account number or any other data field, where the proxy code is store, for example, in data fields on the transaction device 102. Where the proxy code is accompanied by a secondary identifier, such as, for example, a personal identification number (PIN), the issuer system 112 database may correlate or match the proxy code, account number and secondary identifier, so that the issuer system 112 may reference any one of the numbers using any one of the other numbers. The issuer system 112 may use any conventional matching or storage protocol as is found in the art.

In one exemplary embodiment, the issuer system 112 may assign distinct proxy codes for each transaction account the issuer system 112 maintains. In which case, no two transaction accounts would be assigned identical proxy codes. In another exemplary embodiment, the issuer system 112 may assign the same proxy code to a plurality of transaction accounts, to multiple accounts related to the same cardholder, to multiple accounts controlled by the same entity (e.g., corporate card accounts), to all the transaction accounts the issuer system 112 maintains or any other subset of accounts. Moreover, a proxy code may not be a separate code; rather, the proxy code may be derived from the transaction device identifier or any other data. In another embodiment, the proxy code may be contained within another code or account number. In another embodiment, the proxy code is an encrypted or manipulated account number (or any other sensitive information). The same proxy code, an amended proxy code or an additional proxy code may also represent other sensitive data (aside from the account number), such as, for example, account holder name, address, biometric information, demographic information and/or the like. In this regard, the merchant system will not have access to this information, but the proxy code related to this information will be sent to the acquirer when the acquirer requires any portion of this information as part of its approval process.

The proxy code is then loaded onto the transaction device. In other embodiments, the device may generate its own proxy code. In this embodiment, the user may download the generated proxy code to the issuer (e.g., via the Internet) prior to using the code in a transaction. In another embodiment, the reader, POS or merchant system may generate a proxy code prior to, during or after receiving sensitive information. In this embodiment, the reader may delete the sensitive information, and only transmit the proxy code to complete the transaction.

While the transaction device may only contain the proxy code, in certain embodiments, the transaction device may also contain the account number and other sensitive data; however, the transaction device will only communicate the proxy code to the reader. In one exemplary embodiment, the proxy code is configured in magnetic stripe format. That is, the proxy code may be stored in the Track 1/Track 2 portions of the magnetic stripe track network. The proxy code may be uploaded onto a transaction device 102 which the account issuer 112 has assigned to a user (step 230). The proxy code may be uploaded into the transaction device database in magnetic stripe format, and may also be transmitted to the merchant system 101 in similar magnetic stripe format. A suitable method for providing the proxy code to the transaction device 102 may be determined by the transaction device 102 configuration. For example, conventional methods and magnetic stripe read/write devices may be used to encode the proxy code in one location on one of the magnetic stripe tracks. Alternatively, the proxy code may be uploaded into a database or other storage area contained on the transaction device 102, by populating the proxy code on the database using any convention method. A suitable method is described in commonly owned U.S. patent application Ser. No. 10/192,488, entitled “SYSTEM AND METHOD FOR RFID PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” incorporated herein by reference. Once the proxy code is uploaded into the transaction account database, the transaction device 102 may be used for transaction completion (step 208).

In this embodiment, the transaction account may also be assigned a secondary form of identification which may be encrypted, and which may not be available to the merchant system 101. The secondary form of identification may be correlated to the transaction account on the issuer system 112 so that the issuer system 112 may later reference the transaction account for transaction completion.

Once the proxy code is assigned and loaded on the transaction device, the proxy code may be provided during the execution of a transaction in lieu of the actual transaction account number. In this way, the proxy code masks the actual account number from the merchant system 101 and from potential theft. Thus, instead of the merchant system 101 storing the account number for later reference, the merchant system 101 stores the proxy code.

As noted, in one exemplary embodiment, the proxy code is formatted to mimic conventional transaction device sensitive information, such as an account number. Because the proxy code mimics an account number or any other sensitive data and is configured in a format recognizable to the merchant system 101, the merchant system 101 is unable to distinguish between the proxy code and the actual account number. For example, where the actual account number is a credit card number, the proxy code would be configured to take the form of a valid credit card number. Similarly, where the actual account number is a loyalty number, the proxy code is configured in a format similar to a valid loyalty number. In either case, however, the proxy code may contain no or minimal sensitive information related to the user account.

As shown, a secure RFID transaction in accordance with this embodiment may begin when the RFID device 102 enters the interrogation zone of the RFID reader 104 and is interrogated, such as when the transaction device 102 is used to complete a transaction request (step 208). The transaction device 102 information, including the proxy code, device 102 encrypted identifier (where included), and the account issuer 112 routing number, may then be provided to the device processor 114 for transmitting to the RFID reader 104 via RF transmission.

The RFID reader 104 may receive the transaction device 102 information, including the proxy code, and if necessary, convert the information into a POS recognizable format. The converted information may then be provided to the merchant system 101 via POS 106. The merchant system 101 may receive the transaction device information and combine the information with information concerning the requested transaction to produce a transaction request. The transaction information may include a product or merchant location identifier, as well as the terms for satisfying the transaction (e.g., price to be paid, barter points to be traded, loyalty points to be redeemed). Because the proxy code is in the same format as the account number or other sensitive data, the merchant system recognizes the information as valid data for the respective field. The merchant system may then provide the transaction request to an acquirer 110 via a network 108 for transaction request completion.

The acquirer 110 may, in turn, provide the transaction request to the appropriate account issuer 112 for processing (step 212). The acquirer 110 may identify the appropriate account issuer 112 using the routing number provided by the transaction device 102 to locate the network address corresponding to the account issuer 112, thereby permitting the acquirer 110 to provide the transaction request to the account issuer 112 maintaining the corresponding transaction device account.

The account issuer 112 may receive the transaction request and process the transaction request in accordance with the issuer system defined protocol.

The preceding detailed description of exemplary embodiments of the invention makes reference to the accompanying drawings, which show the exemplary embodiment by way of illustration. While these exemplary embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the invention. In addition, the steps recited in any of the method or process claims may be executed in any order and are not limited to the order presented or method steps may be added or eliminated as desired. Further, the present invention may be practiced using one or more servers, as necessary. Thus, the preceding detailed description is presented for purposes of illustration only and not of limitation, and the scope of the invention is defined by the preceding description, and with respect to the attached claims. 

1. A system for completing a transaction using a transaction device comprising: a transaction device associated with a transaction device proxy code, said transaction device comprising a transaction device database for storing said transaction device proxy code.
 2. A system according to claim 1, further comprising a merchant system, said merchant system including a merchant system database, and a point of interaction (POI) device in communication with said transaction device transponder for transmitting and receiving data from said transponder in a contactless environment, the POI in RF communication with said RFID transaction device.
 3. A system according to claim 2, further including a transaction device account issuer system for maintaining a unique transaction account associated with said RFID transaction device, said transaction account correlated to said unique transaction account identifier, said transaction account for use in completing a transaction request.
 4. A system according to claim 3, wherein said transaction device account issuer system provides said unique transaction device account identifier and said transaction device proxy code to said transaction device database, said transaction device proxy code stored on said transaction device database.
 5. A system according to claim 4, wherein said transaction device provides said proxy code and said transaction device identifier to said merchant system POI, said merchant system associating said proxy code and said transaction device identifier to said transaction request.
 6. A system according to claim 5, wherein said merchant system provides at least said transaction device identifier and said transaction request to said issuer system.
 7. A system according to claim 6, wherein said issuer system correlates said transaction device identifier to said unique transaction account, said issuer system satisfying said transaction request relative to said unique transaction account.
 8. A system according to claim 7, wherein said transaction device account identifier is encrypted prior to providing said transaction device identifier to said merchant system.
 9. A system according to claim 8, wherein said encrypted transaction device identifier is decrypted by said issuer system prior to said issuer system correlating said transaction device identifier to said unique transaction account.
 10. A system according to claim 9, wherein said proxy code is unique to said RFID transaction device account.
 11. A system according to claim 9, wherein said proxy code is unique to said issuer system.
 12. A method for completing a transaction in a contactless environment said method including: providing a proxy code and a transaction account identifier to a radio frequency identification (RFID) transaction device; facilitating the providing of said proxy code and said transaction account identifier to a merchant system; facilitating the providing of said proxy code and said transaction device identifier to a transaction device issuer system, said transaction device issuer system maintaining a transaction device account correlative to the transaction account identifier; and facilitating the completion of a transaction request correlative to the transaction device account.
 13. A method according to claim 12, further including correlating the proxy code a distinct transaction device.
 14. A method according to claim 12, further including correlating the proxy code to a distinct transaction account issuer system. 